Fix how the dataset reader uses its device module - #26

Three defects in DatasetReader surfaced while reviewing documentation ahead of the release, two of which made the reader silently wrong. A fourth change renames strict to require_converters, to make its meaning explicit and avoid clashing with the new validate flag.

Preserve the device module type

DatasetReader is now generic over its device module, mirroring Device. device_module returns the module type passed to the constructor, so registers reached through the reader resolve exactly as they do on the module itself.

Match files by the declared device name

A device module now declares the name used to prefix its recordings under DEVICE_NAME, and DeviceModuleLike requires it in place of __name__. The reader takes the file prefix from name when given, then from DEVICE_NAME, then from the folder itself when it holds a single device, which covers a schema that declares no name at all.

The prefix previously came from the module __name__, which is the dotted import path for a pre-generated package, so DatasetReader(behavior, folder) matched no files and a whole session read as empty with no error.

Validate device identity

The reader now compares the module WHO_AM_I against the whoAmI in the folder device.yml, and refuses to construct when they disagree. A module reused across sessions and reaching the wrong folder therefore fails on construction rather than decoding the files against the wrong register map. validate=False turns off every check the reader performs, so a folder whose device.yml is damaged can be read with a module obtained elsewhere.

Rename strict to require_converters

strict is now require_converters on create_registers, create_device_module and create_dataset_reader. Behavior is unchanged. An unresolved custom interfaceType still raises UnknownConverterError, and passing False still decodes it as the native element type.

The old name said nothing about converters, and read as the same kind of switch as the new validate while sitting on the opposite side of the data boundary. validate=False changes whether a check runs, whereas require_converters=False changes the decoded values.